Management of annotated location aware assets

ABSTRACT

A method includes receiving a map indicating a layout of a location, receiving a point-of-interest (POI) data structure representing a POI, and POI metadata associated with the POI, generating an annotated floor map, based on the map, the annotated floor map including a POI indicator placed on the map at the location of the POI, the POI indicator indicating the type of the POI and the status of the POI, displaying at least a portion of the annotated floor map, in response to the client computing device moving within the location or out of the location, transmitting location information to a map selector and receiving one or more maps selected by the map selector, the one or more maps include or bound by the location information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 13/731,309, entitled “Management of Annotated Location AwareAssets”, filed Dec. 31, 2012, which claims priority under 35 U.S.C. §119to Provisional Patent Application Ser. No. 61/717,635, entitled“WORKPLACE ASSET IDENTIFICATION, LOCATION AND CONTEXT AWARE TAGGING ANDSTATUS” filed on Oct. 23, 2012. The subject matter of both applicationsare hereby incorporated by reference in their entirety.

TECHNICAL FIELD

This description relates to asset management, and more specifically tothe tagging and use of physical objects or locations.

BACKGROUND

Typically a company or sufficiently large organization has sharedresources or assets that various people use. In some instances thoseshared resources may include things or physical objects, such as, forexample copiers, printers, fax machines, traveler's workstations orcomputers (e.g., an unassigned computer available for use by travellingor transient workers), etc. In some instances those shared resources mayinclude locations, such as, for example, conference rooms, traveler'sworkstations or “hot” desks (i.e., an unassigned office space availableto travelling or transient workers), etc.

Often times, it may be difficult someone to locate these sharedresources, particularly if one is visiting a corporate site that onedoes not often visit or has never been to. For example, a worker mightwork at a company's Austin site but when that worker visits thecompany's San Jose site, they may find it difficult to locate usableoffice space, or printers, etc. Frequently, even if such a resource isfound (e.g., an empty desk) such a worker may not even know if they areallowed to use the resource. It may be embarrassing for the worker tosit down at and begin to use an empty desk only to find out that thedesk is reserved for someone else. Alternately, it may be frustrating toattempt to use a printer only to find out that the printer is out oforder and that the search for a new printer must begin again. Otherirritations and issues may arise when attempting to use sharedresources.

In some case, even when a desired shared resource is located, theremight be additional steps or actions that may need to be performed oradditional resources may need to be located in order to use theresource. For example, a worker might need instructions on using thevideo or presentation equipment. In another example, even though aworking printer has been found, the printer paper supply might be low orempty and the worker may need to locate more paper.

Likewise, often local or non-traveling employees, members of theorganization, or guests, have a similar need of need to know if adesired resource is available or functional. Traditionally, a workerwould have to physically go to the resource or location and find out itmay or may not be available or functional. For example, to see if aconference room is available, one needs to travel to actual conferenceroom and look to see if anyone is using it. Such a traditional schemecosts valuable time and has the disadvantage of not always beingaccurate (e.g., a conference room may be reserved but the reserver maysimply be late, leading the worker to incorrectly view the emptyconference room as available when it is not, etc.).

Often any of these or other problems may occur and often a worker doesnot know who to contact to resolve the problems or what to do to use theresources correctly and effectively.

SUMMARY

According to one general aspect, a method includes receiving, from aremote computing device, a map indicating a layout of a location,receiving, from the remote computing device, a point-of-interest (POI)data structure representing a POI, and POI metadata associated with thePOI, wherein the POI data structure includes a POI location, and the POImetadata includes a POI type, and a POI status, generating, by a clientcomputing device, an annotated floor map, based on the map, theannotated floor map including a POI indicator placed on the map at thelocation of the POI, the POI indicator indicating the type of the POIand the status of the POI, displaying, via a display interface of theclient computing device, at least a portion of the annotated floor map,in response to the client computing device moving within the location orout of the location, transmitting location information to a map selectorin the remote computing device, and receiving one or more maps selectedby the map selector, the one or more maps include or bound by thelocation information.

According to another general aspect, a non-transitory computer-readablemedium including executable code that, when executed on a processor,cause the processor to perform steps including receiving, from a remotecomputing device, a map indicating a layout of a location, receiving,from the remote computing device, a point-of-interest (POI) datastructure representing a POI, and POI metadata associated with the POI,wherein the POI data structure includes a POI location, and the POImetadata includes a POI type, and a POI status, generating, by a clientcomputing device, an annotated floor map, based on the map, theannotated floor map including a POI indicator placed on the map at thelocation of the POI, the POI indicator indicating the type of the POIand the status of the POI, displaying, via a display interface of theclient computing device, at least a portion of the annotated floor map,in response to the client computing device moving within the location orout of the location, transmitting location information to a map selectorin the remote computing device, and receiving one or more maps selectedby the map selector, the one or more maps include or bound by thelocation information.

According to yet another general aspect, a computing device includes aprocessor and a memory including an application. The application isconfigured to receive, from a remote computing device, a map indicatinga layout of a location, receive, from the remote computing device, apoint-of-interest (POI) data structure representing a POI, and POImetadata associated with the POI, wherein the POI data structureincludes a POI location, and the POI metadata includes a POI type, and aPOI status, generate, by a client computing device, an annotated floormap, based on the map, the annotated floor map including a POI indicatorplaced on the map at the location of the POI, the POI indicatorindicating the type of the POI and the status of the POI, display, via adisplay interface of the client computing device, at least a portion ofthe annotated floor map, in response to the client computing devicemoving within the location or out of the location, transmitting locationinformation to a map selector in the remote computing device, andreceive one or more maps selected by the map selector, the one or moremaps include or bound by the location information.

These and other aspects can include one or more of the followingfeatures. For example, receiving a triggering location, and transmittingthe location information to the map selector can be performed when theclient computing device is one of within a predefined range or within anarea defined by the triggering location. Selecting the maps can be basedon at least one of user actions at the triggering location, or a historyof previously selected maps for the client computing device. The POIdata structure can include a status variable that indicates the statusof the POI represented by the POI data structure and at least one POIaction configured to change the status variable. Selecting the at leastone POI action to be performed can be based on user role informationassociated with the client computing device. Selecting the at least onePOI action to be performed can be based upon a finite state machine. Inresponse to establishing a short-range wireless communication betweenthe client computing device and a particular POI device receiving arequest to perform a first POI action, and causing a first POI action tobe performed. In response to terminating the short-range wirelesscommunication between the client computing device and the POI devicereceiving a request to perform a second POI action, and causing thesecond POI action to be performed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example embodiment of a system inaccordance with the disclosed subject matter.

FIG. 2 is a diagram of an example embodiment of an annotated map inaccordance with the disclosed subject matter.

FIG. 3 is a block diagram of an example embodiment of a system inaccordance with the disclosed subject matter.

FIG. 4 is a block diagram of an example embodiment of a system inaccordance with the disclosed subject matter.

FIG. 5 is a diagram of an example embodiment of an annotated map inaccordance with the disclosed subject matter.

FIG. 6 is a block diagram of an example embodiment of a system inaccordance with the disclosed subject matter.

FIG. 7 is a flowchart of an example embodiment of a technique inaccordance with the disclosed subject matter.

FIG. 8 is a flowchart of an example embodiment of a technique inaccordance with the disclosed subject matter.

FIG. 9 is a flowchart of an example embodiment of a technique inaccordance with the disclosed subject matter.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an example embodiment of a system 100 inaccordance with the disclosed subject matter. In various embodiments,the system 100 may include a user computing system or device 102, a mapor asset management computing system or device 104, one or more storagecomputing devices or systems 106. In some embodiments, the system 100may also include an administrator device 108.

In various embodiments, the user device 102 may include a computingdevice, such as, for example, a laptop, desktop, workstation, personaldigital assistant, smartphone, tablet, and other appropriate computers,etc. or a virtual machine or virtual computing device thereof. Invarious embodiments, the user device 102 may be used by a user 190. Invarious embodiments, the user device 102 may include a processor 112configured to execute one or more machine executable instructions orpieces of software, firmware, or a combination thereof. The user device102 may include, in some embodiments, a memory 114 configured to storeone or more pieces of data, either temporarily, permanently,semi-permanently, or a combination thereof. Further, the memory 114 mayinclude volatile memory, non-volatile memory or a combination thereof.In various embodiments, the user device 102 may include a storage medium115 configured to store data in a semi-permanent or substantiallypermanent form. In various embodiments, the storage medium 115 may beincluded by the memory 114.

In various embodiments, the user device 102 may include one or morenetwork interfaces 116 configured to allow the user device 102 to bepart of and communicate via a communications network. Examples of aWi-Fi protocol may include, but are not limited to: Institute ofElectrical and Electronics Engineers (IEEE) 802.11g, IEEE 802.11n, etc.Examples of a cellular protocol may include, but are not limited to:IEEE 802.16m (a.k.a. Wireless-MAN (Metropolitan Area Network) Advanced),Long Term Evolution (LTE) Advanced), Enhanced Data rates for GSM (GlobalSystem for Mobile Communications) Evolution (EDGE), Evolved High-SpeedPacket Access (HSPA+), etc. Examples of a wired protocol may include,but are not limited to: IEEE 802.3 (a.k.a. Ethernet), Fibre Channel,Power Line communication (e.g., HomePlug, IEEE 1901, etc.), etc. It isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited.

In various embodiments, the user device 102 may include one or moreother hardware components 113 (e.g., a display or monitor, a keyboard, amouse, a camera, a fingerprint reader, a video processor, etc.). It isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited.

In the illustrated embodiment, the user device 102 may include one ormore location services 119. In one such embodiment, the locationservices 199 may be configured to indicate where the user device 102 isphysically located within a certain amount of precision (oftendetermined by the technology used for detecting the location). Invarious embodiments, this location service 199 may include a GlobalPositioning System (GPS) receiver or detector. In another embodiment,the location service 199 may include a control plane locator, such as, adevice configured to determine the distance of the user device 102 fromone or more cell-phone (or other radio signal) towers or broadcasters.In another embodiment, the location service 119 may be configured toestimate the user device's 102 location based upon a time difference ofarrival or other time-based technique. In yet another embodiment, thelocation service 199 may be configured to estimate the user device's 102location based upon a local-range (e.g., <30 meters, Bluetooth, wirelesslocal area network (WLAN) signals, near field communication (NFC),radio-frequency identification (RFID) tags, etc.) signals or anotherform of a local position system (LPS). In various embodiments, thelocation service 199 may be configured to make use of triangulation,trilateration, multilateration, or a combination thereof. In variousembodiments, location service 199 may be configured to make use of oneor more of these examples either in combination or alone. It isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited.

In various embodiments, the user device 102 may include an operatingsystem (OS) 117 configured to provide one or more services to anapplication 118 and manage or act as an intermediary between theapplication 118 and the various hardware components (e.g., the processor112, a network interface 116, etc.) of the user device 102. In such anembodiment, the user device 102 may include one or more nativeapplications, which may be installed locally (e.g., within the storagemedium 115, etc.) and configured to be executed directly by theprocessor 112 and directly interact with the OS 117. In such anembodiment, the native applications may include pre-compiled machineexecutable code. In some embodiments, the native applications mayinclude a script interpreter (e.g., C shell (csh), AppleScript,AutoHotkey, etc.) or a virtual execution machine (VM) (e.g., the JavaVirtual Machine, the Microsoft Common Language Runtime, etc.) that areconfigured to translate source or object code into executable code whichis then executed by the processor 112.

In various embodiments, the user 190 may be travelling to a newenvironment or work place, although the illustrated embodiment would bejust as valid for a location that the user 190 frequents. It isunderstood that the below is merely one illustrative example to whichthe disclosed subject matter is not limited. In such an embodiment, theuser 190 may wish to see or be made aware of the various assets,physical resources, or points of interests (POIs) around the user 190 inthis location.

In such an embodiment, the user device 102 may execute an application118 configured to display a map 128 (e.g., the map 200 of FIG. 2, etc.)to the user 190. This map 128 may include a floor map or map 154 and oneor more points of interest 156.

In this context, a “floor map” includes a map or data structure that maybe interpreted as a geographic diagram of a given or associated locationor route. In this context, a “point of interest” is a term used todescribe both physical objects, such as, for example a copier, printer,fax machine, traveler's workstation or computer, etc. and/or locations,such as, for example, a conference room, desk, etc. In this context, theterm “point of interest” may be used to both describe theobject/location itself or a data structure that represents or isassociated with the physical object/location itself and used torepresent that physical object/location to a computing device (e.g.,those in system 100, etc.) or software application (e.g., application118 of FIG. 1.).

However, while the examples described herein show and describe a floorof an office building, and PoIs that are typical of an officeenvironment (e.g., printers, coffee machines, conference rooms, etc.),it is understood that such are merely a few illustrative examples towhich the disclosed subject matter is not limited. In anotherembodiment, the “floor map” may include a diagram of a rack of serversin data center. In such an embodiment, the PoIs may include variousserver racks or particular server in a given rack. In anotherembodiment, the “floor map” may include a diagram of computer network,and the PoIs may include various computing devices, access points,gateways, servers, and/or routers on the network. It is understood thatthe above are merely a few illustrative examples to which the disclosedsubject matter is not limited.

FIG. 2 is a diagram of an example embodiment of an annotated map 200 inaccordance with the disclosed subject matter. In the illustratedembodiment, the map 200 may include a floor plan or map 290 and one ormore points of interest (e.g., printer 216, etc.). It is understood thatthe above is merely one illustrative example to which the disclosedsubject matter is not limited.

In one embodiment, the map 200 may include the floor plan or map 290. Invarious embodiments, this floor map may show or describe the location ofvarious structural features of a given location (e.g., a floor of anoffice building, etc.). In some embodiments, the structural features mayinclude, but are not limited to, walls, doors, desks, furniture, sinks,toilets, elevators, plants, etc. In some embodiments, these floor maps290 may be stored as images (e.g., a Joint Photographic Experts Group(jpeg) image, bitmap, scalable vector graphic, etc.) or as an array orother data structure that the displaying or manipulating application mayread and display to the user as a human readable floor plan or map.

As described above, in the illustrated embodiment, the map 200 mayinclude one or more points of interest (e.g., printer 216, etc.). Asdescribed above, these PoIs may include physical objects (e.g., printer216, etc.), locations (e.g., conference room 202, etc.), or PoIs thatare a combination of both (e.g., hot desk 244 that includes both acomputer and a workspace, etc.). In various embodiments, these PoIs maybe received by the displaying or manipulating application as a datastructure that is then interpreted and displayed to the user as a humanreadable indicator (e.g., icon, rectangle, etc.).

In the illustrated embodiment, the map 200 may include a number of PoIssuch as, conference room 202; printers 212, 214 & 216; scanner 222;projector 232; and traveler's workstations or hot desks 242, 244, 246 &248. In various embodiments, some of these PoIs may be indicated by anicon or other graphic representation (e.g., text, etc.). In theillustrated embodiment, such PoIs include the printer icons associatedwith the printers 212, 214, and 216; the scanner icon for scanner 222;and the projector icon 232. Conversely, in some embodiments, one or morePoIs may not be indicated by an icon or any graphical indicator or maybe indicated by a coloring or region box or area laid over the floorplan 290. In the illustrated embodiment, such PoIs may include theconference room 202; and the hot desks 242, 244, 248 & 246. In variousembodiments, the PoI icons or indicators may be associated with physicalobjects (e.g., printers, etc.), while the region boxes or non-graphicalindicators may be associated with locations (e.g., conference rooms,kitchens, etc.). It is understood that the above are merely a fewillustrative examples to which the disclosed subject matter is notlimited.

In such an embodiment, the map 200 may indicate where, physically, agiven PoI is located. For example, map 200 indicates that the scanner222 is located on the right-most edge of the floor map 290. In theillustrated embodiment, the map 200 indicates this by placing an iconfor PoI 222 in the same place relative to the floor map 290 as theactual scanner is to the actual floor or office described by the floormap 290. In such an embodiment, a user may determine where physically adesired PoI is.

In the illustrated embodiment, the location of the user or user deviceis displayed by the icon or indicator 201. In such an embodiment, a userthat is searching for a scanner may look at the map 200, locate thescanner 222, themselves (via icon 201), and then determine how to getfrom the location 201 to the location 222 (e.g., walk straight back tothe right-most wall of the floor, etc.). In some embodiments, thedisplaying or manipulating application may to generate and/or display aroute 258 showing the user how to get from their current location 201(or other location) to a desired PoI (e.g., scanner 222, etc.).

In various embodiments, the PoI data structures may include anindication or field that indicates the physical location of PoIassociated with the PoI data structure. In some embodiments, thislocation may be relative to the floor map 290, to another PoI, to acertain point of or on the floor map (e.g., 0.5 feet from the middlewindow of the right wall, etc.). In another embodiment, this locationmay be an absolute location, such as, a GPS coordinate, etc. It isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited.

In various embodiments, the PoI data structures may include anindication or field that indicates the type of PoI associated with thePoI data structure. In various embodiments, these PoI types may describewhat kind of physical object or location the PoI is (e.g., printer,copier, conference room, etc.). In such an embodiment, the displaying ormanipulating application may use this type indication to decide whattype of icon to display on the map 200 (e.g., select a printer icon fora printer typed PoI, select a triangle shape for a toilet, etc.). Inanother embodiment, as described below, the displaying or manipulatingapplication may also use this type indication to decide what defaultactions or states the PoI may be associated with.

In some embodiments, the PoI data structures may include an indicationor field that indicates a sub-type of PoI associated with the PoI datastructure. For example, in one embodiment, a printer-type may includesub-types such as black & white, LaserJet, color, plotter printer, etc.In various embodiments, the PoI sub-type may dictate or alter the iconor indicator used to display the associated PoI. For example, the iconused for a color inkjet printer may differ from the icon used for ablack & white high-volume laser printer. It is understood that the aboveis merely one illustrative example to which the disclosed subject matteris not limited.

In another example, the PoI data structures may include an indication orfield that indicates a property of the PoI associated with the PoI datastructure. In such an embodiment, the property field may include asub-type but may also include other properties such as conference roomcapacity, capabilities of the PoI (e.g., able to print in duplex, etc.).In some embodiments, a PoI may include multiple sub-types and/orproperties. For example, a “multi-use” type PoI may include a “black &white printer” sub-type, a “black & white copier” sub-type, and a “black& white scanner” sub-type. Likewise, a printer PoI may include a“duplex” property, a “1200×1200 dots per inch (dpi)” property, a “500sheets maximum” property, etc. It is understood that the above aremerely a few illustrative examples to which the disclosed subject matteris not limited.

In various embodiments, the PoI data structures may include a “state”property or field that indicates the status or usability of theassociated PoI. In one embodiment, a PoI of conference room or otherlocation type may include a state variable or field of “open”,“reserved”, “in-use”, “closed”, etc. In another embodiment, a PoI ofprinter or other object type may include a state variable or field of“working”, “jammed”, “out of paper”, “out of ink”, “more than 10 jobsqueued”, etc. In such an embodiment, the list of possible states for agiven PoI may vary based upon the type of the PoI. In some embodiments,the list of possible states for a given PoI may be manually set orassigned by an administrator or other user that maintains the map 200(as described below in reference to FIG. 1). It is understood that theabove are merely a few illustrative examples to which the disclosedsubject matter is not limited.

In some embodiments, the map 200 may include one or more indications ofthe particular state of a given PoI. In the illustrated embodiment, theprinter 212 may be jammed or otherwise be associated with a non-workingstate. In such an embodiment, the map 200 may include an icon 252 thatindicates that the printer 22 is in or associated with a non-workingstate. Likewise, the conference room 202 may be “open”, or neither“in-use” nor “reserved” (at the time of day that map 200 is beingdisplayed). In such an embodiment, the map 200 may include an icon 254indicated that the conference room 202 is free for use. It is understoodthat the above are merely a few illustrative examples to which thedisclosed subject matter is not limited.

In various embodiments, the state indicators or icons (e.g., icons 252and 254, etc.) may include an overlay or variation of the type icons orindicators used for the PoIs (e.g., a variation of the printer icon usedfor printer 214, etc.). In various embodiments, the PoI's icon orindicator (e.g., shape, text, etc.) may be color-coded to indicate itsstate or status. In one embodiment, here color codes may be used oremployed. In such an embodiment, green may indicate that the PoI orresource is functional and/or available; yellow or orange may indicatethat the PoI is functional but in use; and red may indicate that theresource is non-functional (e.g., closed for maintenance, jammed, etc.).In some embodiments, the determine as to whether a PoI is “in-use” orany other state may be based upon a predefined threshold, such as, morethan 5 print jobs queued, more than 4 megabytes (MBs) of data queued tothis device, etc. It is understood that the above are merely a fewillustrative examples to which the disclosed subject matter is notlimited.

In some embodiments, a PoI may be associated with one or more actions.In this context, an “action” or “PoI action” includes more or moreprocesses of doing things in order to achieve respective purposesrelated to the PoI. In a preferred embodiment, one or more actions maybe tailored to the PoI-type or properties associated with the PoI. Forexample, actions associated with a conference room PoI may includereserving the conference room at a certain time, removing a conferenceroom reservation, indicating that a conference room is in use, etc. Inanother example, actions associated with a printer PoI may includeprinting a document, filling the printer with paper, rebooting theprinter, deleting a print job form the printer's queue, clearing a paperjam, etc. In another example, actions associated with a coffee machinePoI may include starting the coffee making process, filling the coffeemachine with ingredients (water, filter, coffee beans, etc.). In yetanother embodiment, actions associated with a projector PoI may includeturning the projector on, pairing or placing the projector incommunication with another computing device (e.g., the user's laptop,tablet, etc.), reading an operations manual or instructions leaflet,etc. It is understood that the above are merely a few illustrativeexamples to which the disclosed subject matter is not limited.

In some embodiments, these PoI actions may be broadly divided into twogroups: automated and manual. In such an embodiment, an automated PoIaction may include an action wherein the process of doing the action isperformed by one or more devices (e.g., an external or remote server,the PoI itself, etc.). Examples of such actions may include, printing adocuments, causing a calendaring server application to reserve aconference room, etc. Such actions are described in more detail inrelation to FIG. 3. It is understood that the above are merely a fewillustrative examples to which the disclosed subject matter is notlimited.

In another embodiment, manual actions may include actions that areperformed by a human being (e.g., clearing a paper jam, etc.). In suchan embodiment, the manual action may include a notification that theaction has been performed or is about to be performed. In such anembodiment, the action may cause the state or status of the PoI to bechanged.

In some embodiments, the actions associated with the PoI or displayed tothe user may differ based upon a status of the user. For example, anemployee charged with maintaining Information Technology resources maybe allowed to perform or shown more actions than a normal employee. Inanother example, only employees associated with a particular businessunit or high-level employee may be able to reserve a certain conferenceroom. In various embodiments, the PoI actions may be associated variouslevels of privilege or user groups. It is understood that the above aremerely a few illustrative examples to which the disclosed subject matteris not limited.

In various embodiments, a user mat select (e.g., click on, touch theicon of, etc.) a PoI (e.g., desk 242, etc.). In such an embodiment, inresponse to the user's selection, the displaying or managing applicationmay display a graphical user interface (GUI) element (e.g., menu 256,etc.). In some embodiments, the GUI element 256 may display or offer oneor more actions that the user may select or request be performed (e.g.,reserve the desk 242, request IT help, etc.). In various embodiments,the GUI element 256 or sub-elements (e.g., a menu item, etc.) may, whenselected, cause other GUI elements to be displayed.

In some embodiments, the GUI element 256 may also include the ability toexamine or check the state or status PoI or one or more properties orthe PoI. In the illustrated embodiment, this ability is illustrated bythe menu item “More . . . ”. In another embodiment, the state or aproperty of the PoI may be displayed or indicated in a different manner(e.g., the color overlay, as described above, etc.). In yet anotherembodiment, the state or a property of the PoI may be displayed orindicated via a second GUI element (e.g., a tooltip, a pop-up dialogbox, etc.). It is understood that the above are merely a fewillustrative examples to which the disclosed subject matter is notlimited.

Returning to FIG. 1, as described above, in various embodiments, theapplication 118 may be configured to display a map 128 to the user 190.This map 128 may include a floor plan or map 154 and be annotated withone or more PoIs 156, as described above.

In the illustrated embodiment, the system 100 may include anadministrator device 108. In various embodiments, the administratordevice 108 may include a computing device, such as, for example, alaptop, desktop, workstation, personal digital assistant, smartphone,tablet, and other appropriate computers, etc. or a virtual machine orvirtual computing device thereof. In various embodiments, theadministrator device 108 may be used by a user or administrator 191. Invarious embodiments, the administrator device 108 may include hardwareand/or software components (not illustrated) analogous to thosedescribed above in reference to user device 102.

In various embodiments, the administrator 191 or others like theadministrator 191 may be responsible for populating a database orstorage (e.g., map storage 180, etc.) with one or more floor plans ormaps 164. In some embodiments, the administrator 191 may also beresponsible for populating a database or storage (e.g., map storage 180,etc.) with one or more PoIs 166. Further, in various embodiments, theadministrator 191 may be responsible for maintaining, editing, orupdating these maps 164 and PoIs 164.

In the illustrated embodiment, the administer 191 may use theadministrator user interface (UI) or application 132 to import (and theedit or maintain, etc.) graphic images or data structures that representfloor maps into the map storage 180. In various embodiments, the floormaps 164 may include data that includes a description of the floor map164 (e.g., “Building H, Floor 2”, “Winnipeg Office, Ground Floor”,etc.), and a geographical location or coordinates where the associatedphysical floor exists. In various embodiments, other information may beincluded. In some embodiments, such information may not be stored withinthe floor map 164 itself, but in a separate format as floor map metadata163. In one embodiment, the information may be stored in a variety offormats (e.g., as part of the floor map's 164 filename, as part of ametadata tag include by the floor map, as a separate file, etc.). Invarious embodiments, the floor map metadata 163 and the floor map 164may be stored in a variety of formats, such as for example a text-basedfile (e.g., Extensible Markup Language (XML), JavaScript Object Notation(JSON), Comma-separated values (CSV), etc.), a binary-based format(e.g., zip compression format, JPEG, a serialized object-oriented datastructure or object, etc.), or a combination thereof. It is understoodthat the above are merely a few illustrative examples to which thedisclosed subject matter is not limited.

In the illustrated embodiment, the administrator 191 may use theadministrator user interface (UI) or application 132 to import (and theedit or maintain, etc.) one or more PoIs 166 to the map storage 180. Insome embodiments, the administrator UI 132 may be configured to allow orfacilitate the ability for an administrator 191 to place points ofinterest (PoIs) 166 on the map 164 via a graphical paradigm, similar toplacing items via a drawing program.

In various embodiments, each PoI 166 may include the coordinate(absolute or relative, as described above) of the PoI 166. In someembodiments, the PoI 166 may also include one or more properties suchas, for example, a name of the PoI 166, a PoI type and/or sub-type(e.g., printer, conference room, etc.), a human readable description ofthe PoI (e.g., “Marketing's Printer”, “Conference Room 101”, etc.),etc., as described above. In some embodiments, the PoI such metadata(e.g., type, properties, etc.) may be stored with or as part of the PoI(as illustrated) or as one or more spate files, or a combinationthereof. It is understood that the above are merely a few illustrativeexamples to which the disclosed subject matter is not limited.

As described above, in some embodiments, one or more actions 167 may beassociated with or included by various PoIs 166. In various embodiments,these actions 167 may include, but are not limited to, a phone number(which could integrate with the PoI's native phone features), an emailaddress (which could integrate with the PoI's native email client), auniform resource identifier (URI) or uniform resource locator (URL), aworkflow action which may be integrated with other applications orproducts (e.g., the action handler devices 308 of FIG. 3, the BMC AtriumOrchestrator, a Microsoft Exchange Server, etc.), view a document (e.g.,an instruction or user manual, an office memo, etc.), etc. It isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited.

In some embodiments, one or more of the actions 167 may be associatedwith a specific PoI (e.g., actions for Conference Room 101, etc.). Insuch an embodiment, those PoI specific actions may only be available orvalid for that particular associated PoI 166. Conversely, in anotherembodiment, one or more actions may be associated with a type orsub-type of PoIs (e.g., “print a document” may be associated with allprinters, “reserve the room” may be associated with all conferencerooms, etc.). In such an embodiment, the type-specific actions 166 maybe available or valid for PoIs 166 of that associated type or sub-type.In yet another embodiment, other action grouping or associations may beemployed (e.g., a set of actions 167 valid for all PoIs in the Virgil,Texas office, a set of actions valid for all IT employees, etc.). It isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited.

In the illustrated embodiment, the map and PoI information 162 istransmitted for the administrator device 108 to the map managementcomputing system or device 104, and more specifically to the map and PoImanager 140. In such an embodiment, the map and PoI manager 140 may beconfigured to enter the map or PoI information 162 supplied by theadministrator device 108 into the map storage 180. In variousembodiments, this may include re-formatting the map or PoI information162 for storage as the maps 164 and PoIs 166. Likewise, in theillustrated embodiment, the map and PoI manager 140 may be configured toretrieve maps 164 and PoIs 166 requested by the administrator device 108from the storage device 106 and supply the resultant map or PoIinformation 162 to the administrator device 108. In such an embodiment,an administrator 191 may edit, delete, or update various aspects ofexisting maps 164 and PoIs 166. However, in another embodiment, this mapor PoI information 162 may be communicated directly between the storagesystem 106 and the administrator device 108.

In the illustrated embodiment, the system 100 may include a storagecomputing system or device 106. In various embodiments, the storagedevice 106 may include a computing device, such as, for example, adesktop, workstation, a server, a blade server, and other appropriatecomputers, etc. or a virtual machine or virtual computing devicethereof. In various embodiments, the storage device 106 may includehardware and/or software components 183 analogous to those describedabove in reference to user device 102. In some embodiments, the storagesystem 106 may include a plurality of computing devices.

In various embodiments, the storage system 106 may include one or morestorage systems or data bases 180 and 182. In some embodiments, thestorage system 106 may include a map and PoI storage or database 180. Insuch an embodiment, the map storage 180 may store one or more maps 164and one or more PoIs 166, as described above.

In some embodiments, the storage system 106 may include a PoI statestorage or database 182. In such an embodiment, the PoI state storage182 may include one or more PoI states 168. In various embodiments, eachstored PoI states 168 may be associated with respective PoIs 166. In oneembodiment, the PoI data structures 166 may be associated with orinclude a “state” property or field 168 that indicates the status orusability of the associated PoI 166, as described above. In oneembodiment, the PoI 166 may inherit one or more acceptable states basedon the PoI's type. In another embodiment, the administrator 191 may setor define a list of possible states the PoI 166 may be in. In theillustrated embodiment, the PoI states 168 include the actual state ofthe PoI 166 at a given moment. In such an embodiment, the application118 may display the current state of a given PoI 156 on the annotatedmap 128, as described below.

In the illustrated embodiment, the system 100 may include a mapmanagement (MM) computing system or device 104. In various embodiments,the MM device 104 may include a computing device, such as, for example,a desktop, workstation, a server, a blade server, and other appropriatecomputers, etc. or a virtual machine or virtual computing devicethereof. In various embodiments, the MM device 104 may include hardwareand/or software components 133 analogous to those described above inreference to user device 102. In some embodiments, the MM system 104 mayinclude a plurality of computing devices.

In one embodiment, the MM device 104 may include a map selector 142. Insuch an embodiment, the map selector 142 may be configured to receivelocation information 150 from the user device 102. In one embodiment,the user device 102 may supply or transmit the current location of theuser device 102 periodically or when a triggering event occurs (e.g., inresponse to a user 190 request for a map 154, entering a predefinedlocation, such as, one of the company's offices, etc.). In anotherembodiment, the user device 102 may supply or transmit a request for amap 154 of a specific location 150. In such an embodiment, the user 190may wish to pre-load the user device 102 with one or more maps 154 ofplaces the user 190 is expecting to travel to; although, it isunderstood that the above is merely one illustrative example to whichthe disclosed subject matter is not limited. As described above, invarious embodiments, this location information 150 may include a list ofGPS coordinates or other location coordinates or information.

In some embodiments, the user device 102 or application 118 may havereceived one or more triggering location 121. In such an embodiment,when the user device 102 comes within a predefined range (e.g., 500meters, 10 feet, etc.) or within an area defined by the triggeringlocation 121, the application 118 or user device 102 may transmits itslocation information 150 or a map request that includes the locationinformation 150. In some embodiments, the triggering locations 121 mayinclude a list of GPS coordinates supplied be the MM device 104. It isunderstood that the above is merely one illustrative example to whichthe disclosed subject matter is not limited.

In some embodiments, the map selector 142 may be configured to selectone or more maps 164 that are deemed relevant to the provided locationinformation 150. In one embodiment, the map selector 142 may beconfigured to pick or select a map 164 that includes or bounds theprovided location information 150. For example, if the user device 102is on the third floor of a building, the map selector 142 may select thefloor map 164 of the third floor of that building. In anotherembodiment, the map selector 142 may be configured to select one or mapsnear (as defined by a predefined set of criteria or rules) to thesupplied location information 150. For example, if the user device 102is on the third floor of a building, the map selector 142 may select thefloor maps 164 of the second, third, and fourth floors of that building.In yet another embodiment, the map selector 142 may be configured toremember a history of what maps 164, etc. have previously been presentedto the user device 102. In various embodiments, the map selector 142 maybe configured to take into account user 190 actions or predicted user190 actions when selecting maps 164. For example, if the user device 102is on the third floor of a building, and moving towards the elevators,the map selector 142 may select the floor maps 164 of the second andfourth floors of that building. It is understood that the above aremerely a few illustrative examples to which the disclosed subject matteris not limited.

In various embodiments, the map selector 142 may be configured toretrieve any PoI 166 associated with the selected map 154. In someembodiments, the map selector 142 may be configured to filter or onlyselect a portion of the PoIs 166 associated with the selected map 154,as described below. In one embodiment, the map selector 142 may beconfigured to retrieve any metadata or properties associated with theselected map 154 and the selected PoIs 166. In the illustratedembodiment, this metadata includes the PoI actions 167 and the PoIstates 168. It is understood that the above is merely one illustrativeexample to which the disclosed subject matter is not limited.

In such an embodiment, the map selector 142 may be configured totransmit the selected map 154, the associated or selected PoIs 156, andthe associated PoI metadata 159 to the user device 102. In variousembodiments, this information 154, 156, and/or 159 and othercommunications of system 100 may be transmitted via Hypertext TransferProtocol (HTTP), Hypertext Transfer Protocol Secure (HTTPS), or anothercommunications protocol.

In the illustrated embodiment, the application 118 of the user device102 may include a map annotator 122. In one such an embodiment, the mapannotator 122 may be configured to take the selected map 154 andannotate it with the selected PoIs 156 and the PoI metadata (e.g., type,state, actions, etc.). In one embodiment, the map annotator 122 maygenerate or produce the annotated map 128. In various embodiments, thisannotated map 128 may be similar to the map 200 of FIG. 2.

In the illustrated embodiment, the application 118 may include a mapviewer 124. In such an embodiment, the map viewer 124 may be configuredto display the annotated map 128 to the user 190. As described above, invarious embodiments, the map viewer 124 may be configured to allow theuser 190 to select various PoIs 156, view the state information ormetadata associated with the PoIs 156, zoom in or out of the annotatedmap 128, display a route between two or more locations, select anaction, etc. It is understood that the above are merely a fewillustrative examples to which the disclosed subject matter is notlimited.

In the illustrated embodiment, the map viewer 124 may include a filteror search mechanism 125. In such an embodiment, the user 190 may be ableto limit the PoIs 156 displayed by the map viewer 124 or included withinthe annotated map 128 using a set of criteria supplied or selected bythe user 190. For example, in one embodiment, the user 190 may only wishto see PoIs of type “printer”. In such an embodiment, any PoIs not oftype “printer” may be removed from the annotated map 128 or simply notdisplayed by the map viewer 124. In another embodiment, the filter 125may select or filter PoIs 156 based on other properties or associatedmetadata 159 (e.g., free conference rooms, working copiers, PoIsassociated with the Finance department, PoIs with a “red” state, etc.).It is understood that the above are merely a few illustrative examplesto which the disclosed subject matter is not limited.

In the illustrated embodiment, the map viewer 124 may include a routeror path generating mechanism or component 123. In such an embodiment,the router 123 may be configured to generate or determine a routebetween two or more locations. As described above, in one embodiment,the router 123 may determine a path between the current location of theuser device 102 and a selected or desired PoI 156 (e.g., scanner 222 ofFIG. 2, etc.). In some embodiments, this routine or path may begraphical and displayed on the annotated map 128. In another embodiment,the path may be described in text, graphics, audio directions, acombination thereof, or other forms. It is understood that the above aremerely a few illustrative examples to which the disclosed subject matteris not limited.

In various embodiments, the MM device 104 may include a PoI statemanager 144. In one embodiment, the PoI state manager 144 may beconfigured to maintain the state information 168 associated with eachPoI 166. In such an embodiment, the PoI state manager 144 may receivestate information from a plurality of sources, such as, for example thePoI devices (not illustrated), various user devices 102, or administerdevices 108, etc. In one embodiment, when a printer PoI detects a paperjam, it may be configured to send a message (e.g., email, tweet, HTTPmessage, etc.) to the PoI state manager 144 or a server to which the PoIstate manager 144 subscribes (e.g., a Rich Site Summary or Really SimpleSyndication (RSS) feed, etc.). The PoI state manager 144 may then editor update the PoI state 168 associated with the printer PoI to reflectthe paper jam (e.g., a state of “paper jam”, “unavailable”, etc.).

In such an embodiment, as the state of a selected PoI 156 changes or atpredefined periodic intervals or upon a request from the user device102, the PoI state manager 144 may inform the application 118 of the newor current state. In the illustrated embodiment, this is shown as achange in the PoI metadata 159.

In some embodiments, the system 100 may include PoI transient data (TD)155. In such an embodiment, the PoI metadata 159 may include relativelyor substantially static information (e.g., a list of actions, anassociated file, etc.), and the PoI transient data 155 may includerelatively or substantially dynamic or changing information (e.g., stateinformation, etc.). In some embodiments, the PoI MD 159 may include thePoI TD 155. It is understood that the above are merely a fewillustrative examples to which the disclosed subject matter is notlimited.

In another embodiment, the application 118 in response to receiving theselected PoIs 156 may subscribe to a feed to other publisher source thatbroadcasts changed PoI state information. In various embodiments, thePoI state manager 144 and the application 118 may be configured topartake in a publish-subscribe model of information distribution. It isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited.

In various embodiments, once the application 118 has been notified of achange in state or other metadata 159 of a PoI 156, a new annotated map128 may be generated. In another embodiment, the map viewer 124 maysimply change the way the annotated map 128 is displayed (e.g., a newicon or indicator may be overlaid onto the map 128, etc.). It isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited.

As described above, in various embodiments, a PoI 156 may be associatedwith one or more actions 167, although some PoIs 156 may be associatedwith no actions 167. In the illustrated embodiment, the user 190 mayrequest that an action 167 associated with the PoI 156 occur or hasoccurred. As described above, actions 167 may be broadly categorized asautomatic or manual, although, it is understood that the above is merelyone illustrative example to which the disclosed subject matter is notlimited.

In one embodiment, the application 118 may include a PoI actionresponder 126. In various embodiments, the PoI action responder 126 maybe configured to execute or request the execution of the steps orprocess defined by the selected action 167. In one embodiment, once theuser 190 selects or takes an action 167, the PoI Action responder 126may determine if the action 167 may be executed locally (by the userdevice 102). For example, a user 190 may wish to view a file, or place atelephone call, send an email, etc. If the information needed to executethe action 167 is available locally or may be obtained via localresources (hardware or software), the PoI action responder 126 mayexecute or perform the requested action. For example, the requested filemay be included in the PoI metadata 159 or may be obtainable via an HTTPrequest, the user device 102 may include a phone and the desired numbermay be included in the PoI metadata 159, likewise when sending an email,etc.

Conversely, in some embodiments, the desired action 167 may not be ableto be performed by the user device 102. In such an embodiment, the PoIaction responder 126 may transmit a PoI action request 158 to the MMdevice 104 or other device, as described below, in reference to FIG. 3.In some embodiments, the action 167 may be partially be performedlocally (by the user device 102) and partially performed remotely (e.g.,by the MM device 104). For example, an action 167 may include sending anemail and changing the state or status of the associated PoI. In such anembodiment, the portion of the action 167 that may be performed locallymay be executed or processed by the PoI action responder 144 and theremote portion may be executed by a remote device.

In the illustrated embodiment, the MINI device 104 may include a PoIaction manager 146. In such an embodiment, the PoI action manager may beconfigured to execute or process a PoI action request 158 from a userdevice 102. In various embodiments, the PoI action manager 146 may beconfigured to perform the request action 167 (or portion thereof)itself, or to request that another device perform the action or partthereof.

In one embodiment, the PoI action manager 146 may be configured tochange the state of the PoI 156 associated with the action 168. Forexample, the action 167 may include that the user 190 has cleared thepaper jam in the printer, and the requested action 158 may be to changethe state or status of the printer PoI 156 to reflect that this manualportion of the action 167 has been performed. In some embodiments, thePoI action manger 146 may work with or communicate with the PoI statemanager 144 to perform such an action.

As described above, in such an embodiment, once the PoI's state 168 haschanged the PoI metadata 159 may be updated or re-sent to the userdevice 102. In various embodiments, the PoI transient data 155 may beupdated or re-sent to the user device 102. It is understood that theabove is merely one illustrative example to which the disclosed subjectmatter is not limited.

FIG. 3 is a block diagram of an example embodiment of a system 300 inaccordance with the disclosed subject matter. In various embodiments,the system 300 may include a user computing system or device 302, a mapor asset management computing system or device 304, one or more storagecomputing devices or systems 306, and a state storage system 307. Insome embodiments, the system 300 may also include a one or more actionhandler devices 308.

In the illustrated embodiment, the system 300 differs in a number ofways from the system 100 of FIG. 1. It is understood that the system 300is merely one illustrative example to which the disclosed subject matteris not limited. Various embodiments of the disclosed subject matterexist in which one or more of the differences between system 100 andsystem 300 may be included in the respective embodiment's system.

In one embodiment, the user device 302 may include an application 318similar to the application 118 of FIG. 1. However, in the illustratedembodiment, the application 318 may not be responsible or configured togenerate or create the annotated map 128. In such an embodiment, thegeneration of the annotated map 128 may be done by the MM device 304.

In such an embodiment, the MM device 304 may include a map selector 342,a PoI metadata manager 344, and a map annotator 348. In variousembodiments, the map selector 342 may be configured to select the map154, as described above. Further, in the illustrated embodiment, the mapselector 342 may be configured provide the selected map 154 to the mapannotator 346. In some embodiments, the PoI metadata manager 344 may beconfigured to collect the PoIs 156 and PoI metadata (e.g., PoI state168, PoI actions 167, PoI type, etc.) for the PoIs 356 associated withthe selected map 154. Further, in the illustrated embodiment, the PoImetadata manager 344 may be configured provide the selected PoIs andtheir respective metadata 356 to the map annotator 346.

In the illustrated embodiment, the map annotator 346 may be configuredto take the selected map 154, the selected PoIs and their metadata 356and generate or create the annotated map 128. In such an embodiment, thecomputing or processing load used by the user device 302 may be reducedas the generation of the annotated map 128 is now done by the MM device304. It is understood that the above is merely one illustrative exampleto which the disclosed subject matter is not limited.

In the illustrated embodiment, this annotated map 128 may then besupplied or transmitted to the application 318. It may then be displayedby the map viewer 124. In some embodiments, the annotated map 128 mayinclude a graphical portion (e.g., the floor map 154, icons orindicators for the PoIs 156) and a data structure portion (e.g., PoIactions 167, PoI state information 168, etc.). In such an embodiment,the map viewer 124 may be configured to overlay various information orGUI elements (e.g., an icon color, a menu, etc.) on the graphics portionof the annotated map 128, based upon the data structure portion of theannotated map 128. In such an embodiment, as the data structure portionof the annotated map 128 changes (e.g., a state change of a PoI, etc.)that map annotator 346 may be configured to only transmit to the userdevice 302 the changed information or the change data structure portion.In various embodiments, an initial annotated map 128 may be edited intoa current annotated map 128 by the map viewer in response to changes inPoI metadata. It is understood that the above is merely one illustrativeexample to which the disclosed subject matter is not limited.

In the illustrated embodiment, the filter mechanism 125 and/or therouter mechanism 123 may be included by the map annotator 346. In suchan embodiment, the user device 302 may transmit desired inputs for thesemechanisms (e.g., the filter criteria, the router locations, etc.) viathe location information 150 and the PoI actions 158, respectively. Itis understood that the above is merely one illustrative example to whichthe disclosed subject matter is not limited.

In the illustrated embodiment, the system 300 may include a storagesystem 306. In the illustrated embodiment, the storage device 306 mayinclude separate data bases or stores for the maps 154 (stored in themap storage 380), the PoIs 156 (stored in the PoI storage 382), and theactions 167 (stored in the action storage 386). Further, in theillustrated embodiment, the PoI state information 368 may be stored viaa spate device, state storage system 307. In other embodiments, the mapstorage 380, PoI storage 382, and PoI action 386 may be store togetheror separately in different devices, or database systems. It isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited.

As described above, in various embodiments, the system 300 may includeor be in communication with one or more action handler devices orservices 308. In various embodiments, these action handler service ordevices 308 may be configured to perform various actions requested bythe PoI action manager 348. In one embodiment, the action handlerdevices 308 may be external to the system 300.

In the illustrated embodiment, the MM device 304 may include PoI actionmanager 348. As described above, the PoI action manager 348 may beconfigured to receive a PoI action request 158 from the application 318.As with the PoI action responder 126 of the application 318, the PoIaction manager 348 may be configured to determine if the requested PoIaction 158 may be performed by the MM device 304. If the PoI action 158may be performed, in whole or part, by the MM device 304, the PoI actionmanager 348 may be configured to execute or perform the portions of therequested PoI action 158 that may be performed locally by the MM device304.

However, if the PoI action 158 may not be performed, in whole or part,by the MM device 304, the PoI action manager 348 may be configured todetermine an action handler device 308 that is configured to perform therequested PoI action 158 or a portion thereof. In various embodiments,the PoI action manager 348 may maintain a list or table of actionhandler devices 308 associated with various actions 167 or groups ofactions 167. In some embodiments, this list may be defined or managed byan administrator.

In various embodiments, once the appropriate action handler device orservice 308 has been determined, the PoI action manager 348 may beconfigured to transmit an action request 358 to the determinedappropriate or responsible action handler device 308. In someembodiments, the action handler device 308 may be configured to transmitan action response or acknowledgement (not shown) to notify that PoIaction manager 348 that the action has been performed, failed, or wasaccepted for processing. In such an embodiment, the PoI action manager348 may then take appropriate steps (as defined by the PoI action 158 oran error handling technique, etc.) in response to the action response.

For example, in one embodiment, the action 158 may include reserving aconference room (a PoI 156) for a certain time and date, and sending outemail invitations to a group of people or users 190 to attend a meetingin the conference room (PoI 156). In such an embodiment, the PoI actionmanager 348 may determine that the help of an action handler device 308(e.g., a calendaring system, an email gateway, etc.) is needed tocomplete the action 158. The PoI action manager 348 may then send outone or more action requests 358 to one or more action handler devices308. For example a first action request 358 may be transmitted to a roomreservation system action handler device asking to reserve theconference room for the given time and date. If the first action requestsucceeds, a second action request may be send to an email gateway orserver to send out emails or calendar invitations to the desiredparticipant users. If that is also successful, a message may betransmitted to the user device 302 that the PoI action request 158 wassuccessful. It is understood that the above is merely one illustrativeexample to which the disclosed subject matter is not limited.

In various embodiments, the PoI metadata manager 344 may be configuredto communicate with one or more action handler devices or services 308in order to update that state or other metadata of various PoIs 156. Forexample, once the above conference room has been reserved the MM device304 may not maintain or store the reservation information. As such, theMM device 304 may not know when the given time and date occur, that theconference room PoI's state should be changed to “reserved” (orsimilar). In such an embodiment, the PoI metadata manager 344 may beconfigured to request the reservation status of the conference room-typePoIs from the action handler device 308 responsible for roomreservations. In various embodiments, this information request may occurperiodically. In another embodiment, room reservation system actionhandler device may be configured to notify the MM device 304 when aconference room is reserved. It is understood that the above is merelyone illustrative example to which the disclosed subject matter is notlimited.

FIG. 4 is a block diagram of an example embodiment of a system 400 inaccordance with the disclosed subject matter. In various embodiments,the system 400 may include a user computing system or device 302, a mapor asset management computing system or device 404, and one or morestorage computing devices or systems 406. In some embodiments, thesystem 400 may also include a one or more action handler devices 308.

In the illustrated embodiment, the system 400 differs in a number ofways from the system 100 of FIG. 1 or the system 300 of FIG. 3. It isunderstood that the system 400 is merely one illustrative example towhich the disclosed subject matter is not limited. Various embodimentsof the disclosed subject matter exist in which one or more of thedifferences between systems 100 & 300 and system 400 may be included inthe respective embodiment's system.

In the illustrated embodiment, the system 400 may include a unifiedstorage system or device 406. In such an embodiment, the unified storagesystem 406 may include databases or stores for the maps 154 (via mapstorage 380), the PoIs 156 (via PoI storage 382), the PoI actions 167(via PoI action storage 386), the PoI state information 168 (via PoIstate information storage 388), and the locations 469 of the PoIs (viathe PoI location storage 487). In the illustrated embodiment, thelocations 469 of the PoIs may be stored separately versus as part of thePoIs 156 themselves. In various embodiments, other PoI metadata (e.g.,types, associated documents, etc.) may be stored separately from thePoIs 156. It is understood that the above is merely one illustrativeexample to which the disclosed subject matter is not limited.

In the illustrated embodiment, the MINI computing system or device 404may include a location limiter 445. In various embodiments, the locationlimiter 445 may be configured to limit the PoIs included by theannotated map 428 to PoIs that are within a certain range or distance ofthe user device 302. For example, in one embodiment, the locationlimiter 445 may be configured to remote any PoIs 156 form the annotatedmap 428 or the inputs that are used to generate the annotated map 428,if those PoI locations 469 are greater than 50 feet from the locationinformation 150 provided by the user device 302. In such an embodiment,a user 190 may see more PoIs 156 as they walk through a floor orbuilding, and are not overwhelmed or distracted by PoIs that are notnear them. It is understood that the above are merely a few illustrativeexamples to which the disclosed subject matter is not limited.

In various embodiments, the range may be configurable by the user 190.In such an embodiment, the range may be included by the locationinformation 150. In another embodiment, the range used by the locationlimiter 445 may be predefined. In some embodiments, the range ordistance may take into account the route a user 190 would have to take(e.g., around walls, etc.) between themselves (or the user device 302)and the PoI 158 in question. It is understood that the above are merelya few illustrative examples to which the disclosed subject matter is notlimited.

In various embodiments, the annotated map 428 may not include amonolithic or relatively large image that represents an entire floor orarea. In such an embodiment, the annotated map 428 may include aplurality of tiles that, when displayed together, comprise the entirefloor or area, or a portion thereof. In such an embodiment, the mapannotator 346 may stream or transmit more annotated map tiles to theapplication 318 as the user 190 or user device 304 come with range ofthe newer tiles. In such an embodiment, the annotated map 428 may beupdated piecemeal. In such an embodiment, the location limiter 445 mayfacilitate the determination of which tiles or portions of the annotatedmap 426 are to be transmitted and which the map annotator 346 is torefrain from generating and/or transmitting. It is understood that theabove are merely a few illustrative examples to which the disclosedsubject matter is not limited.

In another embodiment, the annotated map 428 may include all of the PoIs156 associated with map 154. However, the application 318 may include alocation limiter (not shown) or map viewer 124 that may not display orhide the PoIs 156 that are not within a given range. It is understoodthat the above is merely one illustrative example to which the disclosedsubject matter is not limited.

FIG. 5 is a diagram of an example embodiment of an annotated map 500 inaccordance with the disclosed subject matter. In the illustratedembodiment, the map 500 may include a floor plan or map 290 and one ormore points of interest (e.g., printer 216, etc.). It is understood thatthe above is merely one illustrative example to which the disclosedsubject matter is not limited.

In one embodiment, the map 500 may include the floor plan or map 290similarly to the map 200 of FIG. 2. However, in the illustratedembodiment, a number of PoIs (e.g., printer 214 & 212, desks 424, 244,246 & 248, etc.) are missing or not displayed. In the illustratedembodiment, a location limiter has taken the location 201 and determinedwhich PoIs are within a given range (e.g., 25 feet, etc.) of the user'slocation 201.

In various embodiments, only three PoIs (conference room 202, projector232, and printer 216) are deemed to be within range of user 201 and areincluded on map 500. Further, in such an embodiment, if the user 201walks through the office (e.g., towards the wall on the right edge ofthe floor plan 290), the location limiter may add or cause additionalPoIs to be displayed. For example, printer 214, and the desk 242 may bedisplayed.

FIG. 6 is a diagram of an example embodiment of a system 600 inaccordance with the disclosed subject matter. In the illustratedembodiment, the system 600 may include a user computing system or device602, a point of interest device and/or location 603, a map managementcomputing system or device 304, and a storage system 106. In someembodiments, the system 600 may also include one or more action handlerdevices 308.

In various embodiments, the user device 602 may be similar to the userdevice 102 of FIG. 1. In the illustrated embodiment, the user device 602may also include a short-range wireless (SRW) interface orcommunications component 616. In some embodiments, the SRW interface 616may include an interface to a near field communication (NFC) receiver,transceiver, or tag. In such an embodiment, the SRW interface 616 maycommunicate at approximately 13.56±1.8 megahertz (MHz) and may belimited to less than 20 centimeters (cm). In some embodiments, the NCFinterface 616 may operate with an effective range of approximately 4 cm.

In another embodiment, the SRW interface 616 may include an interface toa radio-frequency identification (RFID) transceiver, receiver, or tag.In such an embodiment, the RFID interface 616 may communicate at avariety of frequencies or ranges of frequencies (e.g., 120-150 kHz,13.56 MHZ, 433 MHz, 865-868 MHz, 902-928 MHz, 2450-5800 MHz, 3.1-10 GHz,etc.). Likewise, in some embodiments, the RFID interface 616 maycommunicate at a variety of distances or ranges (e.g., 10 cm, 1 m, 2 m,1-100 m, less than 200 m, etc.).

In yet another embodiment, the SRW interface 616 may include aninterface to a Bluetooth transceiver, receiver, or transmitter. In suchan embodiment, the SRW interface 616 may be configured to operate orcommunicate within the 2400-2480 MHz band. In such an embodiment, theSRW interface 616 may be configured to communicate within one or moreranges (e.g., less than 100 m, less than 10 m, less than 1 m, etc.). Itis understood that the above are merely a few illustrative examples ofshort range wireless communication technologies to which the disclosedsubject matter is not limited.

In the illustrated embodiment, the system 600 may include one or morepoints of interest devices or locations 603. In some embodiments, asdescribed above, the PoI 603 may include a physical device (e.g., aprinter, copier, coffee machine, etc.). In such an embodiment, the PoIdevice 603 may include or have co-located on or near the device (e.g., acircuit attached to a sticker, etc.) that includes the componentsdescribed below. In another embodiment, the PoI device 603 may includeor be integrated with the components described below. In anotherembodiment, as described above, the PoI 603 may include a location(e.g., a conference room, desk, etc.). In such an embodiment, the PoIlocation 603 may include or have co-located within or near the locationa device (e.g., a circuit attached to a sticker or nameplate, etc.) thatincludes the components described below.

In various embodiments, the PoI device or location 603 may include a PoISRW tag 682. In some embodiments, the SRW tag 692 may include more ormore memory elements configured to store information. In someembodiments, the PoI SRW tag 682 may include or store informationrelating to the PoI's 603 state. In various embodiments, the PoI SRW tag682 may include or store information relating to the actions 167associated with the PoI device or location 603. In another embodiment,other pieces of information may be stored by the PoI SRW tag 682.

In the illustrated embodiment, the PoI device or location 603 mayinclude a SRW interface 686. In some embodiments, the SRW interface 686may be similar to the SRW interface 616 of the user device 602. In suchan embodiment, the SRW interfaces 616 and 686 may be configured tocommunicate with one another via one or more message 628. In someembodiments, this communication may be bi-directional. In anotherembodiment, this communication may be unidirectional. In variousembodiments, the nature of communication may depend on the capabilitiesor settings of the PoI device or location 603.

In various embodiments, in response to the messages 628 the PoI deviceor location 603 may alter or edit the state or other information 168stored within the SRW tag 682. For example, in one embodiment, a message628 from the user device 602 may cause the state 168 to change from“reserved” to “in-use”. It is understood that the above is merely oneillustrative example to which the disclosed subject matter is notlimited.

In another embodiment, in response to the messages 628 the PoI device orlocation 603 may transmit the state or other information 168 storedwithin the SRW tag 682 to the user device 602. For example, in oneembodiment, a message 628 from the user device 602 may cause the PoIdevice 603 to transmit the current state 168 or a list of possible orassociated actions 167 to the user device 602. It is understood that theabove is merely one illustrative example to which the disclosed subjectmatter is not limited.

In yet another, less preferred embodiment, in response to the messages628 the PoI device or location 603 may perform or cause to be performedone or more of the actions 167. For example, in one embodiment, amessage 628 from the user device 602 may cause the PoI device 603 totransmit a PoI action request 158 to the MINI device 604. This PoIaction request 158 may be processed by the PoI Action manager 346 of theMM device 304, as described above. It is understood that the above ismerely one illustrative example to which the disclosed subject matter isnot limited.

In various embodiments, the PoI device or location 603 may include oneor more hardware or software components 683 analogous to the hardwarecomponents, 112, 113, 114, 115, 116, 117, etc. of the 602 user device asdescribed above. For example, in one embodiment, a network interface(e.g., to a local area network (LAN), WLAN, cellular network, etc.) maybe employed to communicate a PoI action request 158 to the MM device 304or other communications as desired.

In a more preferred embodiment, upon communicating with the SRWinterface 686 of the PoI device 603 the user device, the PoI ActionResponder 626 of the user device 602 may transmit a PoI action request158 to the MM device 304. In such an embodiment, this PoI action request158 may be processed by the PoI Action manager 346 of the MM device 304,as described above.

In various embodiments, an example interaction between the user device602 and the PoI device 603 may include when an employee enters aconference room PoI, the user 190 may place their cell phone or userdevice 602 on an NFC tag or device 603. Once the user device 602 hasacknowledged the PoI device 603 (via the NFC interface 616), the userdevice 602 may be configured to transmit a PoI action request 158 thatincludes a request to change the state of the conference room PoI from“reserved” to “in-use”.

In another embodiment, the PoI action request 158 may include a requestto indicate that the user 190 of the user device 602 in now attendingthe meeting. In such an embodiment, the user device 602 may include oneor more pieces of user role information 622. In such an embodiment, theuser role information 622 may include the name or username of the user190. In another embodiment, the user role information 622 may include agroup to which the user 190 belongs (e.g., administrator, IT group,etc.), a title associated with the user 190, or other identifyinginformation about or associated with the user 190. In variousembodiments, the PoI device 603 may be configured to filter or restrictmessages or information (e.g., actions, etc.) communicated to the userdevice 602 based upon the user role information 622. It is understoodthat the above are merely a few illustrative examples to which thedisclosed subject matter is not limited.

In another example embodiment, an IT support person may enter a room tofix a projector PoI. In such an embodiment, the IT person may placetheir user device 602 on the PoI device 603 or otherwise cause the SRWinterface 616 to communicate with the SRW interface 686. In oneembodiment, the communication or messages 626 may cause the application618 to display a UI element (e.g., a dialog box, etc.) to the user 190.In some embodiments, this may only occur if the user role information622 indicates that the user 190 of the user device 602 has IT supportresponsibilities. The UI element may ask the user 190 if a maintenanceaction is being performed. In such an embodiment, the suggested orrequested action 167 may be based upon the state 168 of the PoI device603. For example, if a printer PoI is jammed, the dialog box may ask ifthe user 190 has cleared the jam. In one embodiment, the user 190 maymanually select that the action 167 has been performed, and a PoI actionrequest 158 may be sent to the MM device 304.

In another embodiment, a second triggering event (e.g., removing theuser device 602 from communication with the PoI device 603) may cause adefault PoI action request 158 to be sent to the MM device 304. Forexample, if the PoI device 603 is in an operable or usable state (e.g.,no printer jam, etc.) and a user 190 indicates that a maintenanceactivity or action is being performed, the PoI's state 168 may bechanged to “inactive” or “under maintenance”. When the user 190 removestheir user device 602 from communication with the PoI device 603 (anexample of a triggering act or event), the PoI device 603 or, in apreferred embodiment, the user device 602 may initiate a PoI actionrequest 158 that returns the PoI state 168 to an operable or usablestate. In some embodiments, the PoI device 603 may be configured toreceive state 168 or other information updates via a WLAN or LAN messageor communication from the MM device 304. It is understood that the aboveis merely one illustrative example to which the disclosed subject matteris not limited.

In such an embodiment, the PoI device 603 or the user device 602 mayinclude a finite-state machine (FMS) or similar set of rules that allowsthe PoI device 603 to proceed through a series of states 168 or possibleactions 167 based upon a set of triggering events (e.g., starting theSRW communication, ending the SRW communication, received messages 628,etc.). In such an embodiment, the FSM may be stored in the same memoryhardware component 683 that stores the state 168 and action 167information. In another embodiment, the FSM may be delivered to the userdevice 602 in response to an initial PoI action request 158. It isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited.

While the above examples have described the PoI device 603 as havinglimited computational ability and the user device 602 as having agreater computational ability (e.g., initiating the PoI action requests158, display UI elements, etc.) this may not be true in all embodiments.In some embodiments, the PoI device 603 may have the greatercomputational ability (e.g., initiating the PoI action requests 158,display UI elements, etc.) and the user device 602 the lessercomputational ability, relative to one another. In some suchembodiments, user device 602 may not include the application 618, OS117, or other hardware components besides the SRW interface 616 (e.g.,processor 112, a display, a storage medium 115, etc.).

In one such example embodiment, a cleaning employee's user device 602may include a badge, card, or other such device. In such an embodiment,when a cleaning employee 190 enters a toilet/restroom or other locationPoI, the cleaning employee 190 may swipe, scan, or otherwise place theiruser device 602 in brief communication with a PoI device 603 locatedwithin the location PoI. In such an embodiment, the initial triggeringevent (placing the devices 602 & 603 in communication) and the user roleinformation 622 that indicates the user 190 is part of the cleaningstaff, may cause the location PoI's state 168 to change to “beingcleaned”. Likewise, when the cleaning employee leaves, against swipingtheir user device 602 or ending the SRW communication and causing asecond triggering event, the location PoI's state 168 to change to“available”. In such an embodiment, the PoI device 603 may beresponsible or configured to send the PoI action request 158 to changethe state 168.

In such an embodiment, the change in state of the associated PoIs (e.g.,the toilet “being cleaned”, the projector “under maintenance”, etc.) maybe communicated to the user device 602 or similar user devices of otherusers (not shown) via an updated annotated map or updated PoI metadata,as described above. In such an embodiment, an engineering employee maybe able to see that the toilet closest to them is “being cleaned” anddecide to use another functional toilet instead. It is understood thatthe above is merely one illustrative example to which the disclosedsubject matter is not limited.

In some embodiments, the SRW interface 616 may be able to act as asecondary or supplemental location aid. In one such embodiment, if anemployee finds that a PoI is “unavailable”, the application 602 maycommunicate with other PoIs within the range of the SRW protocolemployed by the SRW interface 616 to determine if any other PoI devices603 are in an “available” state and match the same type as the“unavailable” PoI. In such an embodiment, the application 612 may promptor display a UI element to the user 190 before making this discoveryattempt.

In another embodiment, the PoI devices 603 in communication with the SRWinterface 616 may be used by a location limiter (e.g., similar to thelocation limiter 445 of FIG. 4, etc.) to determine what PoIs to displayon the annotated map. In such an embodiment, the user device 602 mayinclude a location limiter (not shown). It is understood that the aboveis merely one illustrative example to which the disclosed subject matteris not limited.

In various embodiments, the MM device 304 may be configured to collectusage statistics or information regarding the SRW communication betweenvarious PoI device 603 and user device 602. For example, in oneembodiment, a count may be maintained by the MM device 304 every time auser device 602 and a PoI device 603 initiate communication. In variousembodiments, this information may be transmitted to the MM device 304 byeither the user device 602 or the PoI device 603. Likewise, the lengthof an interaction or communication session, the user roles 622 of theusers 190, the actions 167 requested or communicated to the user devices602, etc. may also be monitored and recorded. It is understood that theabove are merely a few illustrative examples to which the disclosedsubject matter is not limited. In such an embodiment, the statisticalinformation may be used by an administrator or other user to determinewhat PoIs are being used and how they are being used.

FIG. 7 is a flowchart of an example embodiment of a technique 700 inaccordance with the disclosed subject matter. In various embodiments,the technique 700 may be used or produced by the systems such as thoseof FIG. 1, 3, 4, or 6. Furthermore, portions of technique 700 may be useor produce maps such as that of FIG. 2, 4, or 5. Although, it isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited. It is understood thatthe disclosed subject matter is not limited to the ordering of or numberof actions illustrated by technique 700.

Block 701 illustrates that, in one embodiment, a floor map, apoint-of-interest (POI) data structure, and/or point-of-interestmetadata may be requested, as described above. In some embodiments,these items may be requested from a remote computing device, asdescribed above. In various embodiments, requesting may include or occurin response to detecting that an apparatus or user device has physicallyentered a triggering location, as described above. In variousembodiments, one or more of the action(s) illustrated by this Block maybe performed by the apparatuses or systems of FIG. 1, 3, 4, or 6, theapplications 118, 318, and/or 618 of FIG. 1, 3, 4, or 6, as describedabove.

Block 702 illustrates that, in one embodiment, a floor map indicatingthe structural layout of a predefined physical location may be received,as described above. In some embodiments, the floor map may be receivedfrom a remote computing device, as described above. In one embodiment,receiving the floor map may include receiving an initial annotated floormap from the remote computing device, wherein the annotated floor mapincludes the floor map and the POI data structure, as described above.In various embodiments, one or more of the action(s) illustrated by thisBlock may be performed by the apparatuses or systems of FIG. 1, 3, 4, or6, the applications 118, 318, and/or 618 of FIG. 1, 3, 4, or 6, asdescribed above.

Block 704 illustrates that, in one embodiment, one or morepoint-of-interest (POI) data structures representing respectivepoints-of-interest may be received, as described above. In someembodiments, the PoIs may be received from a remote computing device, asdescribed above. In one embodiment, receiving the PoIs may includereceiving an initial annotated floor map from the remote computingdevice, wherein the annotated floor map includes the floor amp and thePOI data structure, as described above.

In some embodiments, the point-of-interest data structure may include alocation of an associated POI that is associated with thepoint-of-interest, as described above. In one such embodiment, the PoImay be associated with a physical location, as described above. Inanother embodiment, the PoI may be associated with a physical apparatusor device, as described above. In various embodiments, one or more ofthe action(s) illustrated by this Block may be performed by theapparatuses or systems of FIG. 1, 3, 4, or 6, the applications 118, 318,and/or 618 of FIG. 1, 3, 4, or 6, as described above.

Block 706 illustrates that, in one embodiment, point-of-interestmetadata associated with the point-of-interest may be received, asdescribed above. In some embodiments, transient data associated with thepoint-of-interest may be received either a part of the metadata orseparately, as described above. In some embodiments, the PoIs may bereceived from a remote computing device, as described above. In oneembodiment, the point-of-interest metadata includes a point-of-interesttype indicating a type of the associated POI, and a point-of-intereststatus indicating the status of the associated POI, as described above.In another embodiment, the PoI metadata may include at least one POIaction that may be performed in relation to the POI, as described above.In such an embodiment, the POI action may include an action that changesa state variable of the associated PoI, as described above. In variousembodiments, one or more of the action(s) illustrated by this Block maybe performed by the apparatuses or systems of FIG. 1, 3, 4, or 6, theapplications 118, 318, and/or 618 of FIG. 1, 3, 4, or 6, as describedabove.

Block 708 illustrates that, in one embodiment, an annotated floor mapmay be generated based, at least in part, upon the floor map, asdescribed above. In one embodiment, the annotated floor map may includea point-of-interest indicator, as described above. In one suchembodiment, the point-of-interest indicator may be placed on the floormap at the location of an associated point of interest and may indicatethe type of the associated point of interest and/or at least part of thestatus of the associated point of interest, as described above. In someembodiments in which an initial annotated map has been received,generating an annotated floor map may include altering the initialannotated map based upon the POI metadata, as described above. Invarious embodiments, one or more of the action(s) illustrated by thisBlock may be performed by the apparatuses or systems of FIG. 1, 3, 4, or6, the applications 118, 318, and/or 618 of FIG. 1, 3, 4, or 6, asdescribed above.

Block 710 illustrates that, in one embodiment, at least a portion of theannotated floor map may be displayed, as described above. In someembodiments, this portion may be displayed via a display interface of auser device, as described above. In various embodiments, one or more ofthe action(s) illustrated by this Block may be performed by theapparatuses or systems of FIG. 1, 3, 4, or 6, the applications 118, 318,and/or 618 of FIG. 1, 3, 4, or 6, as described above.

Block 712 illustrates that, in one embodiment, a request by a user todisplay more information regarding the POI may be received, as describedabove. In various embodiments, in response to this request, additionalPOI metadata may be requested, for example, from the remote computingdevice, as described above. In some embodiments, once the additional POImetadata has been received, the additional POI metadata may be displayedto the user, as described above. In various embodiments, one or more ofthe action(s) illustrated by this Block may be performed by theapparatuses or systems of FIG. 1, 3, 4, or 6, the applications 118, 318,and/or 618 of FIG. 1, 3, 4, or 6, as described above.

Block 714 illustrates that, in one embodiment, a request to perform aPOI action may be received, as described above. In one embodiment, inresponse to this request it may be determined if the POI action mayand/or must be performed either wholly locally or requires theassistance of the remote computing device, as described above. In suchan embodiment, if the performance of the POI action requires assistanceof the remote computing device, a POI action request message may betransmitted, to the remote computing device, as described above. In onesuch embodiment, the request may include the message to perform at leasta portion of the POI action, as described above.

In some embodiments, receiving a request to perform a PoI action mayinclude establishing a communication via a near field communication orSRW protocol with a PoI, as described above. In such an embodiment,requesting may also include requesting the performance of the POI actionin response to establishment of communication with the POI via the nearfield communication or SRW protocol, as described above. In variousembodiments, one or more of the action(s) illustrated by this Block maybe performed by the apparatuses or systems of FIG. 1, 3, 4, or 6, theapplications 118, 318, and/or 618 of FIG. 1, 3, 4, or 6, as describedabove.

FIG. 8 is a flowchart of an example embodiment of a technique 800 inaccordance with the disclosed subject matter. In various embodiments,the technique 800 may be used or produced by the systems such as thoseof FIG. 1, 3, 4, or 6. Furthermore, portions of technique 800 may be useor produce maps such as that of FIG. 2, 4, or 5. Although, it isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited. It is understood thatthe disclosed subject matter is not limited to the ordering of or numberof actions illustrated by technique 800.

Block 802 illustrates that, in one embodiment, a plurality of floor mapsmay be stored, as described above. In various embodiments, storing mayinclude the use of a memory device, as described above. In someembodiments, each floor map may indicate the structural layout of arespective predefined physical location, as described above. In variousembodiments, one or more of the action(s) illustrated by this Block maybe performed by the apparatuses or systems of FIG. 1, 3, 4, or 6, thestorage systems 106, 306, and/or 406 of FIG. 1, 3, 4, or 6, as describedabove.

Block 804 illustrates that, in one embodiment, a plurality ofpoint-of-interest (POI) data structures may be stored, as describedabove. In various embodiments, each point-of-interest data structure mayinclude a physical location of an associated POI that is associated withthe respective point-of-interest data structure, as described above. Insome embodiments, each POI data structure may be associated with atleast one POI metadata that includes a point-of-interest type indicatinga type of the respective associated POI, and a point-of-interest statusindicating the status of the respective associated POI, as describedabove. In various embodiments, one or more of the action(s) illustratedby this Block may be performed by the apparatuses or systems of FIG. 1,3, 4, or 6, the storage systems 106, 306, 307, and/or 406 of FIG. 1, 3,4, or 6, as described above.

Block 806 illustrates that, in one embodiment, point-of-interestmetadata associated with each respective point-of-interest datastructure may be stored, as described above. In various embodiments,each point-of-interest metadata may include a point-of-interest typeindicating a type of the respective associated POI, and apoint-of-interest status indicating the status of the respectiveassociated POI, as described above.

In various embodiments, one or more of the action(s) illustrated by thisBlock may be performed by the apparatuses or systems of FIG. 1, 3, 4, or6, the storage systems 106, 306, 307, and/or 406 of FIG. 1, 3, 4, or 6,as described above.

Block 808 illustrates that, in one embodiment, a floor map request maybe received from a client computing device, as described above. In someembodiments, the floor map request may include a requested location, asdescribed above. In one embodiment, the floor map request may includeone or more filtering criteria, as described above. In variousembodiments, one or more of the action(s) illustrated by this Block maybe performed by the apparatuses or systems of FIG. 1, 3, 4, or 6, themap management systems 104, 304, and/or 404 of FIG. 1, 3, 4, or 6, asdescribed above.

Block 810 illustrates that, in one embodiment, a selected floor mapand/or a selected subset of the plurality of POI data structures may beselected, as described above. In some embodiments, this selection mayoccur based upon the location included by the floor map request, asdescribed above. In various embodiments, selecting may includedetermining a subset of the plurality of POI data structures based upona distance between the requested location and the physical location ofan associated POI that is associated with the respective POI datastructure, as described above. In yet another embodiment, selecting aselected subset of the plurality of POI data structures may includeselecting a POI data structure only if the POI data structure passes thefiltering criteria, as described above. In various embodiments, one ormore of the action(s) illustrated by this Block may be performed by theapparatuses or systems of FIG. 1, 3, 4, or 6, the map management systems104, 304, and/or 404 of FIG. 1, 3, 4, or 6, as described above.

Block 812 illustrates that, in one embodiment, a response to the floormap request based upon the selected floor map and the selected POI datastructures may be transmitted, as described above. In some embodiments,the response may be transmitted to the client computing device, asdescribed above. In some embodiments, transmitting may includegenerating an annotated floor map, based upon the selected floor map, asdescribed above. In such an embodiment, the generated annotated floormap may include, for each selected POI data structure, a selectedpoint-of-interest indicator, wherein the point-of-interest indicator isplaced on the floor map at a location representing the physical locationof the respective associated POI and indicates both the type of theassociated POI an at least part of a status of the associated POI, asdescribed above. In such an embodiment, transmitting may also includetransmitting, at least in part, the annotated floor map to the clientcomputing device, as described above.

In one embodiment, transmitting may include dividing the annotated floormap into a plurality of tiles, as described above. In such anembodiment, transmitting may also include transmitting, to the clientcomputing device, one or more of the tiles as a user requests to view aportion of the annotated floor map that includes the transmitted tiles,as described above. In various embodiments, one or more of the action(s)illustrated by this Block may be performed by the apparatuses or systemsof FIG. 1, 3, 4, or 6, the map management systems 104, 304, and/or 404of FIG. 1, 3, 4, or 6, as described above.

Block 814 illustrates that, in one embodiment, a request may be receivedfrom the computing device to perform a POI action in regards to one ofthe POIs, as described above. In some embodiments, in response to therequest a determination as to whether or not the POI action may beperformed either wholly locally or requires the assistance of a remotecomputing device may be made, as described above. In variousembodiments, if the performance of the POI action requires assistance ofthe remote computing device, a POI action request message may betransmitted, to the remote computing device, as described above. In suchan embodiment, the request may include a request to perform at least aportion of the POI action, as described above. In various embodiments,one or more of the action(s) illustrated by this Block may be performedby the apparatuses or systems of FIG. 1, 3, 4, or 6, the map managementsystems 104, 304, and/or 404 of FIG. 1, 3, 4, or 6, as described above.

Block 816 illustrates that, in one embodiment, a change in the POImetadata associated with at least one selected POI data structure may bedetected, as described above. In various embodiments, in response to thedetection, an update message may be transmitted to the client computingdevice, as described above. In various embodiments, the update messagemay include a change to the POI metadata and/or POI transient data, asdescribed above. In various embodiments, one or more of the action(s)illustrated by this Block may be performed by the apparatuses or systemsof FIG. 1, 3, 4, or 6, the map management systems 104, 304, and/or 404of FIG. 1, 3, 4, or 6, as described above.

FIG. 9 is a flowchart of an example embodiment of a technique inaccordance with the disclosed subject matter. In various embodiments,the technique 900 may be used or produced by the systems such as thoseof FIG. 1, 3, 4, or 6. Furthermore, portions of technique 900 may be useor produce maps such as that of FIG. 2, 4, or 5. Although, it isunderstood that the above are merely a few illustrative examples towhich the disclosed subject matter is not limited. It is understood thatthe disclosed subject matter is not limited to the ordering of or numberof actions illustrated by technique 900.

Block 902 illustrates that, in one embodiment, a short-range wirelesscommunication may be established between a user device and apoint-of-interest (POI) device, as described above. In variousembodiments, the PoI device may be associated with a PoI data structurethat represents a physical PoI, as described above. In one embodiment,the POI device may be located within the physical POI, and the physicalPOI may be a room, as described above. In various embodiments, one ormore of the action(s) illustrated by this Block may be performed by theapparatuses or systems of FIG. 1, 3, 4, or 6, the user computing device102, 302, and/or 602 of FIG. 1, 3, 4, or 6, as described above.

Block 904 illustrates that, in one embodiment, a POI action to beperformed may be determined, as described above. In one embodiment, thedetermination may be based, at least partially, upon user roleinformation associated with the user device, as described above. Inanother embodiment, the determination may be based, at least partially,upon a finite sate machine, as described above. In another embodiment,determining may include or may occur after a list of possible POIactions is read, via the short-range wireless communication, from thePOI device, as described above. In various embodiments, one or more ofthe action(s) illustrated by this Block may be performed by theapparatuses or systems of FIG. 1, 3, 4, or 6, the user computing device102, 302, and/or 602 of FIG. 1, 3, 4, or 6, and/or the PoI device 603 asdescribed above.

Block 906 illustrates that, in one embodiment, a request to perform aPOI action in regards to the physical POI may be received, as describedabove. In some embodiments, the POI data structure may include a statusvariable that indicates the status of the physical POI represented bythe POI data structure, as described above. In such an embodiment, thePOI action may include changing the status variable included by the POIdata structure, as described above. In another embodiment, receiving arequest to perform a POI action may include receiving, in response toestablishing the short-range wireless communication between a userdevice and a point-of-interest (POI) device, a request to perform afirst POI action, as described above. In various embodiments, one ormore of the action(s) illustrated by this Block may be performed by theapparatuses or systems of FIG. 1, 3, 4, or 6, the user computing device102, 302, and/or 602 of FIG. 1, 3, 4, or 6, as described above.

Block 908 illustrates that, in one embodiment, the POI action may becaused to be performed, as described above. In various embodiments,causing may include changing a POI indicator associated with the POIdata structure on an annotated floor map, as described above. In such anembodiment, the annotated floor map may include a floor map and at leastone point-of-interest indicator, wherein the point-of-interest indicatoris placed on the floor map at a location dictated by an associated POIdata structure, as described above.

As described above, in one embodiment, the request to perform a PoIaction may include a request to perform a first PoI action. In such anembodiment, causing the POI action to be performed may include causingthe first POI action to be performed, as described above. In someembodiments, in response to terminating the short-range wirelesscommunication between a user device and a point-of-interest (POI)device, a request to perform a second POI action may be received, asdescribed above. In such an embodiment, the second POI action may becaused to be performed, as described above. In various embodiments, oneor more of the action(s) illustrated by this Block may be performed bythe apparatuses or systems of FIG. 1, 3, 4, or 6, the user computingdevice 102, 302, and/or 602 of FIG. 1, 3, 4, or 6, as described above.

Block 910 illustrates that, in one embodiment, usage data associatedwith the POI device may be transmitted to a usage monitoring device, asdescribed above. In some embodiments, the usage data may include a timeat which the short-range wireless communication was established betweenthe user device and the point-of-interest (POI) device. In variousembodiments, one or more of the action(s) illustrated by this Block maybe performed by the apparatuses or systems of FIG. 1, 3, 4, or 6, theuser computing device 102, 302, and/or 602 of FIG. 1, 3, 4, or 6, asdescribed above.

Implementations of the various techniques described herein may beimplemented in digital electronic circuitry, or in computer hardware,firmware, software, or in combinations of them. Implementations may beimplemented as a computer program product, i.e., a computer programtangibly embodied in an information carrier, e.g., in a machine-readablestorage device or in a propagated signal, for execution by, or tocontrol the operation of, data processing apparatus, e.g., aprogrammable processor, a computer, or multiple computers. A computerprogram, such as the computer program(s) described above, can be writtenin any form of programming language, including compiled or interpretedlanguages, and can be deployed in any form, including as a stand-aloneprogram or as a module, component, subroutine, or other unit suitablefor use in a computing environment. A computer program can be deployedto be executed on one computer or on multiple computers at one site ordistributed across multiple sites and interconnected by a communicationnetwork.

Method steps may be performed by one or more programmable processorsexecuting a computer program to perform functions by operating on inputdata and generating output. Method steps also may be performed by, andan apparatus may be implemented as, special purpose logic circuitry,e.g., an FPGA (field programmable gate array) or an ASIC(application-specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random access memory or both. Elements of a computer may include atleast one processor for executing instructions and one or more memorydevices for storing instructions and data. Generally, a computer alsomay include, or be operatively coupled to receive data from or transferdata to, or both, one or more mass storage devices for storing data,e.g., magnetic, magneto-optical disks, or optical disks. Informationcarriers suitable for embodying computer program instructions and datainclude all forms of non-volatile memory, including by way of examplesemiconductor memory devices, e.g., EPROM, EEPROM, and flash memorydevices; magnetic disks, e.g., internal hard disks or removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor andthe memory may be supplemented by, or incorporated in special purposelogic circuitry.

To provide for interaction with a user, implementations may beimplemented on a computer having a display device, e.g., a cathode raytube (CRT) or liquid crystal display (LCD) monitor, for displayinginformation to the user and a keyboard and a pointing device, e.g., amouse or a trackball, by which the user can provide input to thecomputer. Other kinds of devices can be used to provide for interactionwith a user as well; for example, feedback provided to the user can beany form of sensory feedback, e.g., visual feedback, auditory feedback,or tactile feedback; and input from the user can be received in anyform, including acoustic, speech, or tactile input.

Implementations may be implemented in a computing system that includes aback-end component, e.g., as a data server, or that includes amiddleware component, e.g., an application server, or that includes afront-end component, e.g., a client computer having a graphical userinterface or a Web browser through which a user can interact with animplementation, or any combination of such back-end, middleware, orfront-end components. Components may be interconnected by any form ormedium of digital data communication, e.g., a communication network.Examples of communication networks include a local area network (LAN)and a wide area network (WAN), e.g., the Internet.

While certain features of the described implementations have beenillustrated as described herein, many modifications, substitutions,changes and equivalents will now occur to those skilled in the art. Itis, therefore, to be understood that the appended claims are intended tocover all such modifications and changes as fall within the scope of theembodiments.

What is claimed is:
 1. A computing device comprising: a processor; adisplay interface; and a memory including an application configured to:receive, from a remote device, a map indicating a layout of a location;receive, from the remote device, a point-of-interest (POI) datastructure representing a POI, and POI metadata associated with the POI,wherein the POI data structure includes a POI location, and the POImetadata includes a POI type, and a POI status; generate an annotatedfloor map based on the map, the annotated floor map including a POIindicator placed on the map at the location of the POI, the POIindicator indicating the type of the POI and the status of the POI;display, via the display interface, at least a portion of the annotatedfloor map; in response to the computing moving within the location orout of the location, transmitting location information to a map selectorin the remote device; and receiving one or more maps selected by the mapselector, the one or more maps include or bound by the locationinformation.
 2. The computing device of claim 1, wherein the applicationis further configured to receive a triggering location, whereintransmitting the location information to the map selector is performedwhen the computing device is one of within a predefined range or withinan area defined by the triggering location.
 3. The computing device ofclaim 2, wherein selecting the maps is based on at least one of: useractions at the triggering location, or a history of previously selectedmaps for the computing device.
 4. The computing device of claim 1,wherein the POI data structure further includes a status variable thatindicates the status of the POI represented by the POI data structureand at least one POI action configured to change the status variable. 5.The computing device of claim 4, wherein the application is furtherconfigured to select the at least one POI action to be performed basedon user role information associated with the computing device.
 6. Thecomputing device of claim 4, wherein the application is furtherconfigured to select the at least one POI action to be performed basedupon a finite state machine.
 7. The computing device of claim 1, whereinthe application is further configured to: in response to establishing ashort-range wireless communication between the computing device and aPOI device: receiving a request to perform a first POI action, andcausing a first POI action to be performed; and in response toterminating the short-range wireless communication between the computingdevice and the POI device: receiving a request to perform a second POIaction, and causing the second POI action to be performed.
 8. A methodcomprising: receiving, from a first device, a map indicating a layout ofa location; receiving, from the first device, a point-of-interest (POI)data structure representing a POI, and POI metadata associated with thePOI, wherein the POI data structure includes a POI location, and the POImetadata includes a POI type, and a POI status; generating, by a seconddevice, an annotated floor map based on the map, the annotated floor mapincluding a POI indicator placed on the map at the location of the POI,the POI indicator indicating the type of the POI and the status of thePOI; displaying, via a display interface of the second device, at leasta portion of the annotated floor map; in response to the second devicemoving within the location or out of the location, transmitting locationinformation to a map selector in the first device; and receiving one ormore maps selected by the map selector, the one or more maps include orbound by the location information.
 9. The method of claim 8, furthercomprising: receiving a triggering location; and transmitting thelocation information to the map selector is performed when the seconddevice is one of within a predefined range or within an area defined bythe triggering location.
 10. The method of claim 9, wherein selectingthe maps is based on at least one of: user actions at the triggeringlocation, or a history of previously selected maps for the seconddevice.
 11. The method of claim 8, wherein the POI data structureincludes a status variable that indicates the status of the POIrepresented by the POI data structure and at least one POI actionconfigured to change the status variable.
 12. The method of claim 11,further comprising selecting the at least one POI action to be performedbased on user role information associated with the second device. 13.The method of claim 11, further comprising selecting the at least onePOI action to be performed based upon a finite state machine.
 14. Themethod of claim 8, further comprising: in response to establishing ashort-range wireless communication between the second device and a POIdevice: receiving a request to perform a first POI action, and causing afirst POI action to be performed; and in response to terminating theshort-range wireless communication between the second device and the POIdevice: receiving a request to perform a second POI action, and causingthe second POI action to be performed.
 15. A non-transitorycomputer-readable medium including executable code that, when executedby a processor, cause the processor to perform steps comprising:receiving, from a first device, a map indicating a layout of a location;receiving, from the first device, a point-of-interest (POI) datastructure representing a POI, and POI metadata associated with the POI,wherein the POI data structure includes a POI location, and the POImetadata includes a POI type, and a POI status; generating, by a seconddevice, an annotated floor map based on the map, the annotated floor mapincluding a POI indicator placed on the map at the location of the POI,the POI indicator indicating the type of the POI and the status of thePOI; displaying, via a display interface of the second device, at leasta portion of the annotated floor map; in response to the second devicemoving within the location or out of the location, transmitting locationinformation to a map selector in the first device; and receiving one ormore maps selected by the map selector, the one or more maps include orbound by the location information.
 16. The non-transitorycomputer-readable medium of claim 15, wherein the steps further include:receiving a triggering location; and transmitting the locationinformation to the map selector is performed when the second device isone of within a predefined range or within an area defined by thetriggering location.
 17. The non-transitory computer-readable medium ofclaim 16, wherein selecting the maps is based on at least one of: useractions at the triggering location, or a history of previously selectedmaps for the second device.
 18. The non-transitory computer-readablemedium of claim 15, wherein the POI data structure further includes astatus variable that indicates the status of the POI represented by thePOI data structure and at least one POI action configured to change thestatus variable.
 19. The non-transitory computer-readable medium ofclaim 18, wherein the steps further include selecting the at least onePOI action to be performed based on user role information associatedwith the second device.
 20. The non-transitory computer-readable mediumof claim 18, wherein the steps further include selecting the at leastone POI action to be performed based upon a finite state machine.